Remote Desktop Connections suck at event queuing

Microsoft Remote Desktop Connections are great when the network is working. When there's a brief lag in the connection, events are queued. Great. The problem is that keyboard events and mouse events are in DIFFERENT QUEUES!! The network just lagged for me, so I clicked in a location in a text editor and typed a word. When the lag passed, my events went through, but the word was typed at the old cursor location, and then the mouse click went through and jumped the cursor to the new place. Would it really have been that hard to buffer all input in the same queue?? Come on!