An unexpected behavior:
After doing a route calculation, the altitude of all maps drawn after the route cal are zoomed out a bit...looks like 10-15% or so. In other words, maps retrieved before a route calculation at an altitude of 75 will be a bit more zoomed in than all the maps retrieved at that same altitude after the route calc.
Querying the map objects's altitude
with objMap.Altitude.Tostring does report the correct altitude of the requested map and is the same before and after the route calc.
My hack/workaround so far is to create 2 seperate mappoint applications and 2 seperate map objects, and then just use 1 of them to create routes so it doesnt distort the other one.
As always, I am sure I am missing something simple.