Then again, it may not be strictly due to /fp:precise - I tried compiling with VS2010 too, and even though it was /fp:precise the bug did not manifest itself.
Perhaps comparing assembly code would have given a definite answer, but since it is so obvious from source I don't think it is worth the effort.
