Found a solution to avoid round-down in printing coordinates.

Passing the position through the coordinates constructor after setting the precision and creating a string,
 ie creating an new instance based on the string representations, corrects the 60.00 issue. Stupid.