Thank you very much for all the information that you provided in this thread.

It has been fixed in the report. The fix will go to the 3.3 release.