First time I've tried punching in with Platinum.  I had a song completed but the singer decided to redo the vocal track.  We started at the beginning and part way through the singer messed up.  I stopped the recording and punched him (it was after an instrumental break) and he recorded to the end of the song.  When I stopped the recording and went back, the punched in portion had changed position.  For example I punched him in at marker point 52, but after the recording stopped the punched in portion was positioned at marker point 45.   I did it several times and each time it did the same thing.  I closed down Sonar, restarted and tried again and it still did the same thing.   I finally had the singer redo the entire vocal track (he was able to go through the complete song) and it recorded OK. 
 
I've punched in singers many times with X3 Producer and older versions.  This is the first time I've done it with Platinum.  I haven't changed anything in Sonar - its the defaults.
 
The fix, as I posted, As WDM works. I deleted the aud.ini file, restart Sonar with the WDM mode.  Switched to ASIO and it worked!   brundelfly's suggestion of the aud.ini seems to be a key or at least a key in this.

I'm marking this Solved.  I tried it to day, several times and could not duplicate the problem. 
 
Chalking it up to "FM".
 

Jack,
 
I had the same thing happen a couple of weeks ago and never did figure out what was the cause. I thought it was just me. Strange!!
 

fireberd
I'm marking this Solved.  I tried it to day, several times and could not duplicate the problem. 
 
Chalking it up to "FM".
 

I was going to say this sounded like some miscommunication between SONAR and your audio driver about sample position. Re-initialization of the driver on reboot may have been necessary to fix it.
 
 

I don't think it was a driver problem with my Roland Studio-Capture.  It was recording when I punched in, just that after the recording was done Sonar repositioned it.  The driver can't reposition what was recorded.   

No, but SONAR interacts with the driver to determine what sample position it was at when the recording started. If that was misreported or SONAR misread it, the record latency compensation could be based on a faulty value, causing the audio to be compensated to the wrong position after recording stops.
 
 

I recorded a new track (complete track) and it worked OK, no "repositioning".   There was a space at the beginning as there was the count in and the instrumental intro before the voice track started and it didn't reposition that. 

I've had something similar happen when looping a section and recording takes. It was off about a measure IIRC, and I could still use the takes by moving them to the correct location. If I turned off the looping feature, it recorded normally. It's happened two or three times and the fix was turning off looping. I realize this may be a slightly different scenario than yours, but someone else may have had this happen.

Ran into the exact same issue today. Still on X3e as a result of trying to recover from Q1 snow delays, but have run into this on numerous occasions when tracking vocal takes. It appears to be related to either punching in takes on a loop or using the metronome count in. if I get a 24 hr break, i'll try to document a repeatable set of conditions.  

When this happened to me, I "fixed" it by turning off the metronome. I had a 2-bar count-in and somehow that was screwing up Sonar's timing. I didn't need the count for the punches I was doing, but if I had I would have considered this a serious problem.