Destructor/Constructor hotspot during CPU profiling?

I did a CPU profiling of my game ("ExampleGame") and I got some strange results:

For some reason in the top 5 the hotspots from my code is constructor and destructor of vectors. It is wierd considering the destructor has no side effects, and the constructor just initializes the members (all simple floats)

I had imagined matrix multiplication would be the definate hotspot, considering it is much more heavy.

I am running a debug build though. Is it some debug environment stuff causing this result?

The math library is GLM and the profiler is AMD Code XL