It's a good question. You almost have to think about how your corporate network is designed more then anything. I mistakenly created DMZ subnet a while back with a 192.168.0.0/24 address. Now some users log into netconnect and are coming from a 192.168.0.0/24 network, obviously it creates a problem. This is the reason why I can't do split tunneling.
If you keep all server resources a 10. address I think you'll find that a majority of your remotes will be coming from a 192.168.0.0 range.
One thought I have is that perhaps you could create a Host Checker Policy that checks the source IP and alerts them if there was a conflict. I cringe at the thought of pushing all those routes down to users. You'll have to update that every time you make a change.
I always wondered if NAT would be a good solution. (is anyone doing this?) I'd love to get all my remotes on Virtual Machines back here. Would solve a lot of our problems.
Sorry to ramble. I look forward to other posts on this issue.