Erik Darling explains why SET STATISTICS TIME ON can give you different timing results from what the execution plan states:
Here are the relevant details:
SQL Server Execution Times:
CPU time = 3516 ms, elapsed time = 3273 ms.What looks odd here is that CPU and elapsed time are near-equal, but the plan shows parallelism.
Thankfully, with operator times, the actual plan helps us out.
The query itself ran for <900ms.
The answer makes perfect sense.