Copying short non-overlapping chunks of memory is common in a lot of workloads (think manipulation of short strings) and it does happen in tight loops where an overlap check with two additions, two comparisons and two branches is a comparable amount of work to what memcpy() does.<p>Why should I have to manually implement memcpy() for small sizes when I know the memory won&#x27;t overlap?