Well, tough one there.
There are instances where we need UsePrecisePositioningForText to make a report export well. Then there are instances where we don't want it as it causes your issue. The question then is, which one is the bug? UsePrecisePositioningForText, on or off?
In order for me to raise this to R&D I need your report (UsePrecisePositioningForText off), which I have, and a report that needs UsePrecisePositioningForText on to work correctly. I will look back at when they introduced the UsePrecisePositioningForText option, see if there is a report attached there.
- Ludek