kawika
Although the Redbook issue may be in play. I suspect Chuckebaby has the correct diagnosis because  many of my Sonar Projects begin at the very first measure.
 
What is the most effective way to move  song's content (many songs with 24-30 tracks with audio, midi, and automation)? 
 
Oh...and (just occurred to me)...What if?: Will Sonar export from multi to 2-track without error given a bar-1 starting point? If so, I could transfer the 2 tracks to something like Soundforge wherein you see the files and make sure there is sufficient space between tracks?

I've had some try to debate this, but I have found (in my travels) that by starting content at the 1:01 on the timeline...Burning or even export doesn't pick up on the first few milliseconds, sometimes even more than that of the material.
Midi may react differently, by I know for a fact Audio does.
Thus every project I create starts 1 bar in (@ 2:01). A simple 4 count. just like the old analog days ;-)
 
Hit select all (SHIFT+A) and drag your content over to bar 2:01 and do a quick test.
this will at minimum inform you if this is indeed your problem.

I, too, have long practiced starting songs after 1 measure for this very reason: a note that begins exactly at 00:00:00 will nearly always be missing a few milliseconds at the front.
 
However, I assumed that not to be the OP's problem for two reasons. First, he stated that playback is OK. Second, he says it's about 100ms that's being lopped off, far more than the 00:00:00 phenomenon causes.

I still start songs at measure 2 as well. Initially was a midi on issue, but a habit that has continued for 20 years because it is safe.

What the problem is remains something of a mystery. There are three possibilities. The first is that the burning process somehow truncates/loses the data. The second is that the data is still there ready to play, but that the starting overhead of the CD player takes so long to begin the play that it runs into the song data, or more accurately does not start to produce audible output until the beginning of the data has passed. Like an automobile, a CD player and software does not go zero to 60 instantly. The third is that there is an error in the pointer to the location of the song beginning encoded in the cda file so that it starts the song after the beginning of the data. Disc at once files do not have actual breaks in the data continuity between songs, the songs are accessed separately by using the location information in the cda file. One test that might be tried is to rip the burned CD and then examine the wave file in a audio editor to see if the data is missing. The problem is that some of the same latency problems that cut off audible playback might carry over into the ripping process, so that a ripped wave that is truncated doesn't solve the problem. But a ripped wave that is complete would rule out any real truncation in the burning process.
 
In any event padding the beginning of the wave with silence in an audio editor prior to burning would give time for the playback latency to be covered. Automatic or manual gap inclusion in a dedicated Red Book burner would have the same effect. It is doubtful that the song address pointer or truncation in the burning process is the problem. 

bitflipper
I, too, have long practiced starting songs after 1 measure for this very reason: a note that begins exactly at 00:00:00 will nearly always be missing a few milliseconds at the front.
 
However, I assumed that not to be the OP's problem for two reasons. First, he stated that playback is OK. Second, he says it's about 100ms that's being lopped off, far more than the 00:00:00 phenomenon causes.

I wasn't debating you or anything man. I hope it didn't seem like that.
I could be totally wrong in my opinion of what is happening here.
TBH, im probably wrong more than I am right on this forum

Thanks guys...You've all given me several things to investigate. They all seem plausible. Unfortunately, I will be away from my studio till the weekend. I will let you know what the problem was when I get back.

kawika
Thanks guys...You've all given me several things to investigate. They all seem plausible. Unfortunately, I will be away from my studio till the weekend. I will let you know what the problem was when I get back.

well please keep us informed. I would like to know what was causing this.
(so I can be right...cough...cough... )