Some people teach that for deep dives planned on tables--including tables generated by software programs--a certain descent rate is assumed. On a shallow dive, it won't make much difference if you exceed it. On a very deep dive, a faster ascent rate means you spent more time at the deepest part of your dive than the dive plan expected. Roughly calculating the case James described above, the program/table might assume the diver spend the first 3 minutes of the dive at an average depth of 100 feet, when in reality those 3 minutes were at an average depth of 170 feet.
I don't know if that is the reason in this case, but I do know that people who dive tables and descend significantly faster than the assumed rate might want to consider themselves as having had more bottom time than normal.
I don't know if that is the reason in this case, but I do know that people who dive tables and descend significantly faster than the assumed rate might want to consider themselves as having had more bottom time than normal.