Duration in protocol of webconsole and in Table doesn't match

Hi there,

I just started with Azure Functions and I am currently looking into execution times. When I invoke a Function directly from the webconsole for testing, the protocol under the code shows me the duration of that execution. When I look into the corresponding Table in my Storage Account I can find the execution Id related to the test I made in the webconsole. Unfortunately, the StartTime and EndTime in the Table doesn't match the duration in the protocol of the webconsole. If I go to the monitoring page the last invocations of that function are listed and here the duration matches the StartTime and EndTime I can see in the table, but it's again different from the duration from the protocol in the webconsole.

Is there a difference in how the protocol in the webconsole calculates the duration and how the monitoring / Table does it?

#### Investigative information

Please provide the following:

- Timestamp: 2017-07-15T22:30:27.929Z
- Invocation ID: 0907ee53-a088-487c-9b7d-045784449992
- Region: eu-west

#### Repro steps

Provide the steps required to reproduce the problem:

1. Create new Javascript Function / open existing one in developer webconsole
2. Execute Function with some kind of testdata
3. Note the duration the protocol is showing
4. Open the monitoring tab of that Function and note the duration that is displayed there
5. Check if there is a difference
6. [Optional] go into the storage account and look at the Table of the Function
7. [Optional] find the execution id and note the StartTime and EndTime and calculate the duration
8. [Optional] compare that duration with the duration from the protocol in the developer webconsole and from the monitoring tab (should be equal to monitoring tab, but not to the protocol)

#### Expected behavior

All three places where the duration of a Function is logged should have the same duration.

#### Actual behavior

The duration shown in the developer webconsole protocol doesn't match the duration in the monitoring tab and in the Table.

#### Known workarounds

I guess the correct duration is the one from the monitoring tab and from the Table, not that one from the developer webconsole protocol.

#### Related information

Provide any related information

* Programming language used: javascript
* Links to source: I just used the javascript that is auto-generated when a new Function is created