*  Thanks Plugh for pointing out that the constructor that takes a ulong regionhandle and saves it to to X,Y vars in the OpenSim.Framework.Location object was inverting the X and Y resulting in X and Y confusion.    The test also used 256x256 in the uint,uint constructor so it was unable to determine if the X and Y components swapped.   I don't expect much upheaval from this commit, not a lot of features were using the ulong Location object constructor.   The database never stores the ulong regionhandle...    the prims are loaded by region Guid.   LLUDPServer used it to determine regions that it handled in a service definition where there was simply a X == X test which has the same logical result un-switched as it did switched.   Again, thanks LibOMV for the regionhandle code.