Useless sfTimer::startTimer() call in sfTimerManager::getTimer()

uhm.. it would break existing functionality. as currently getTime() will reset the starttime. But I am not sure if this is intentional. Perhaps its not even unnecessary but even a bug.

(In [12807]) [1.1, 1.2] removed unneeded code (closes #4287)

self::$timers[$name]->startTimer();

is necessary when a timer is called many times. In symfony 1.1.5, when sfTimer::addTime() method is called, it adds the time since the first call of the timer, instead of the last one. It results on huge, unreal times.

I suggest to go back to :

<?php
  public static function getTimer($name)
  {
    if (!isset(self::$timers[$name]))
    {
      self::$timers[$name] = new sfTimer($name);
    }

    self::$timers[$name]->startTimer();

    return self::$timers[$name];
  }

?>

(In [13339]) [1.1, 1.2] reverted r12807 (closes #4287)