Assume that you use query_plan_profile and query_post_execution_plan_profile extended events (XEvents) in SQL Server 2017. When you examine the Event Fields CPU time and elapsed time for these XEvents, you may notice that they are less accurate (always multiples of 100) when compared to the same Event Fields reported by the equivalent XEvent query_post_execution_showplan that uses normal profiling.
This issue is fixed in the following cumulative update for SQL Server:
About cumulative updates for SQL Server:
Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. Check out the latest cumulative updates for SQL Server: