This looks like the sort of time creep that you would see with the local schedular service if you tell it to do an inventory scan (or a vulscan) every 24 Hrs without a time window. The 24hr clock starts from the time the last task completed.. I wonder how this scheduling is actully implemented :-) I must look into this a bit more...
It's exactly the same thing. The difference is that I can set a time window for my inventory (2am - 6am). I can't do that for Content Replication. The time window avoids schedule creep.