We've investigated it a little bit more, and indeed there is a bug in the RenderObject method that causes this (it had tried it with FlexCelImgExport, which is the most common way to render files, and that was ok, that's why I couldn't reproduce it).
But now it should be fixed, I hope we can finish the new release by the end of next week.