Thank you for the response. 3.6.2 did not fix the problem unfortunately. I did some testing on the issue to help track down the problem. First off, I tested on a different machine using the same project, and the delay worked correctly on this machine. The machines are both Windows XP. The failing computer was running the project from a network drive for back up purposes, and the passing computer was running from a local copy. I created a new local project on the failing machine with just a delay test step, and the extra time was still observed. The actual time taken seems to vary though. This run took over 6 minutes for example. The failing computer has a faster processor than the other machine, so I would not think it is a performance issue. The CPU usage never goes over 5%. I also tried reinstalling the software and rebooting the machine, but I did not have any success with this either.
