Re: memcpy overlap: quickly detect, diagnose, work around