Oh come on...
When you have to manage a large and complex network, you need to ensure that the traffic is prioritised so that 'stuff that must get through now' (AKA Real-time traffic) gets through in real time and 'stuff that ain't that important' (AKA the other sh!t) gets through when it can. In reality, this only matters when the pipes are full.
VM are going to offer (up to) 50Meg. Now seriously, they aren't going to have a backbone here that is 50 Meg* number of subscribers, so in order to make the best use of the network when it is full or near full, they will de-prioritise some traffic. I did it with large, complex networks that I was responsible for and it resulted in a better experience for everyone. Why? Simple. Because things like VoIP, video conferencing and http/https traffic got priority, and they are the things that people see happening in real time and are affected by other things blocking the network. Stuff like SMTP, FTP, BitTorrent, BITS and so on can get deprioritised because essentially the end user doesn't really see the difference.
-So your email turns up 2 seconds later than it would have. Problem?
-So your Torrent download takes 3 minutes instead of 2 minutes 40. Is that really a problem?
You will probably suffer more from latency than from prioritisation if your torrent source(s) are far far away.
Having said all of this, VM only needs to look at packet headers to see what sort of traffic it is & it definitely shouldn't be looking at packet contents, which would be a breach of trust in my opinion.
People here are sooo quick to jump to a conclusion and pour forth with an opinion. At least nobody has *welcomed our packet sniffing overlords* etc. thank god.