This bug also affects version 5.0.3. The test in the PU demostrates the bug. It alos contains a 'fix'. Not sure, if it is the correct solution.