boost::geometry::intersection still broken with integer coordinates

[aar@…]

When loading these geometries as integer coordinates, their intersection is equal to the input multilinestring, which is wrong because the line should be clipped to the polygon boundaries instead of being left untouched.

POLYGON((500000 853554,146445 500000,500000 146445,853554 500000)) MULTILINESTRING((163696 853553,163696 146446))

If I scale these input coordinates down by 1/1000, the result is correct. Also, no issues when loading the same input as double coordinates.

[aar@…]

Also, same operation on same input coordinates worked correctly with Boost < 1.52.