Fix the ping timeout bug that gives incorrect "reply timed out" messages in Server 2012r2 and Windows 10 for pings under 1000ms timeout
Ping can take a timeout, if the timeout is set less than 1000ms then genuine replies start getting ignored as timed out failures.
Does not affect Server 2003 or 2008.
Does affect Server 2012 r2 and Windows 10
Appears to be a problem in WinAPI / networking stack rather than .Net or ping.exe implementation - happens at ICMPSendEcho2Ex and ICMP6SendEcho2Ex layers at least.