I think that a typical mouse can only move (signed byte) pixels in X and Y diections in a given message, if this protocol is still in use:
http://en.wikipedia.org/wiki/Mouse_(computing)#PS.2F2_interface_and_protocol
Although, couldn't programatically moving the mouse around escape this limitation? I know that WM_MOUSEMOVE messages use two bytes and just say the final location of the mouse, so there's no 'one byte' limitation there. If you programatically move the mouse more than 128 pixels it would just create 'one mouse movement' not chunk it up, right?
Finally, my understanding is that a mice informing the computer about a mouse movement is interrupt based (so can happen as often as it wants, whenever it wants) - so any game that polls for mouse movement once per frame instead of learning about it via interrupts can have arbitrarily far mouse movements in one frame, regardless of above concerns.