Yes, I also think there's something wrong about the CCC code.
The thing is - the latest issues with CCC and avast (not the initial ones, in the first release of avast! 6.0, that was avast's fault indeed) were simply caused by the fact that the corresponding files were scanned. The scanning slightly delayed loading/starting of the executables... and CCC failed to start.
However, similar delay can be caused by a slow computer... or other programs running/starting on background... or Windows writing a block of memory into the swap file... many possibilities.
So yes, I definitely believe similar problems can occur on machines without avast!, and more or less randomly - because it's a timing issue.