RC: Remove an incorrect comment.

Bug: 755840
Change-Id: I5eba22ebcc2e8a11c1d0df7d249b0dd5c0aa5066
Reviewed-on: https://chromium-review.googlesource.com/1175847
Commit-Queue: Sigurður Ásgeirsson <siggi@chromium.org>
Commit-Queue: Chris Hamilton <chrisha@chromium.org>
Reviewed-by: Chris Hamilton <chrisha@chromium.org>
Cr-Commit-Position: refs/heads/master@{#583306}

chrome/browser/resource_coordinator/render_process_probe.cc

@@ -186,10 +186,6 @@ void RenderProcessProbeImpl::ProcessGlobalMemoryDumpAndDispatchOnIOThread(
   UMA_HISTOGRAM_COUNTS_1000("ResourceCoordinator.Measurement.TotalProcesses",
                             batch->measurements.size());
 
-  // TODO(siggi): Because memory dump requests may be combined with earlier,
-  //     in-progress requests, this is an upper bound for the start time.
-  //     It would be more accurate to get the start time from the memory dump
-  //     and use the minimum of the two here.
   batch->batch_started_time = collection_start_time;
   batch->batch_ended_time = base::TimeTicks::Now();