I ran the test case against 5.2.10 and I could not reproduce the problem. Is it possible this is related to something more specific to your environment?