Not really. The problem in Apache is not "not merging", but O(N^2)
memory consumption while handling Range requests, where N - number
of ranges requested.
Sure, but it hits even badly when it does not check overlapping/same range
request. I guess nginx would send back 416 when it
encounters overlapping ranges (?) and the patch from Igor takes care of
exceeding content length case.