Bug: End of game clock

[Logan]

I'm not sure if this is a "known" bug (search function isn't working for me right now, as I keep getting error messages), so I apologize if I'm repeating something.

Just played in the FOF Bowl, as the Jets against the Giants. I'm not much for play-calling, but I'll pick it up occassionally. This is one situation where I did.

Anyway, tie game and I'm driving down the field late, with all my timeouts still remaining. After the two minute warning, I'm close to FG range, so I start trying to grind out the clock. Here's the log of the last few plays:


New Jersey: Weak formation with two tight ends, strength is left. The defense is in a 43 and weak-side man, otherwise cover-7 zone coverage, keying aggressively on the run.
1-10-NYK17 (4Q: 00:35) Brady Quinn spiked the ball to stop the clock.
New Jersey: I formation, strength is left. The defense is in a 43 and weak-side man, otherwise cover-7 zone coverage, keying aggressively on the pass.
2-10-NYK17 (4Q: 00:31) Adrian Peterson ran inside the right guard for 3 yards. Tackled by DT Barry Cofield.
New Jersey: I formation, strength is left. The defense is in a 43 and weak-side man, otherwise cover-7 zone coverage, expecting the pass. Arrington and Dixon are blitzing.
3-7-NYK14 (4Q: 00:25) Adrian Peterson ran inside the right tackle for 6 yards. Tackled by DT Quinn Pitcock, assisted by S Luther Bradford.
New Jersey won the coin toss and will receive to begin overtime.


When I picked the last play, with 25 seconds left, I specifically looked at the bottom of the play call screen to make sure it didn't say "time will expire if you do not call a timeout." So it takes 25 seconds for a simple inside run? When I saw the clock read 0 after the play, I was shocked. Luckily, I ended up winning the game in overtime.

Anyone else see something like this? Am I repeating something that's been noted 12 times?

*Edit to add that this is with 6.0b.