physics.bounds now correctly match game.world.bounds on system start

Previously assumed the world always had (x,y) === (0,0) which is not always the case.