I agree, at the moment sticking with 2016 seems like the way forward at least for running projects, at least for now.
Thanks everyone whose taken the time to confirm the issue and suggest workarounds.
@JimW Could you log this as a bug please. Also what's the current (2016/2017) best practice on working to OS coordinates, this thread suggests a few options; user origin, draw far away from the internal origin, create a local coordinate system (keep track of offset external to VW).
Thanks
Tobias