Peter, this issue has now been fixed in revision 69568. We are awaiting authorization to post the fix into our 6.0 release.