The problem is due to MS implementing of floating point arithmetic - See http://support.microsoft.com/kb/78113 and http://answers.microsoft.com/en-us/o...b-68b599b31bf5

It is NOT a bug although it looks like it