John, what we're really looking for is confirmation that this is still an issue on ORM 4. Has anyone tried the attached test case on a newer version?