[Beta 5 Bug] Vector<> Does Not Sort Properly with dQsort()

I noticed this while working with MeshRoad. If you create a long, winding road and then do a container raycast that intesects multiple meshroad segments, they do not get sorted correctly by qsort in MeshRoad::castRay(). The sorted array should be from closest segment to farthest segment, so that the collision code can early-out, but they always end up sorted from farthest to closest, even if you reverse the logic of the qsort callback. With the array sorted backwards, the hit point ends up on the farthest segment instead of the nearest. It looks like the problem is qsort does not work properly with the Vector<> template class, because I replaced "Vector<MeshRoadHitSegment> hitSegments" with a regular array, "MeshRoadHitSegment hitSegments[]", and it sorted properly.

There are places all over the code where a Vector<> is sorted with dQsort(), which makes me think there are many places that suffer from this problem and could potentially be the culprits behind some really strange and hard to find bugs.