I think most of the uglynes in the c++ template case comes from the tool not resolving the standard types. Just replacing the std::string boilerplate reduces it

I think most of the uglynes in the c++ template case comes from the tool not resolving the standard types. Just replacing the std::string boilerplate reduces it by roughly half. 0.00 0.00 32187/32187 std::vector<std::pair<std::string,int> >::vector<std::__detail::_Node_iterator<std::pair<std::string const, int>, false, true>,void> ( std::__detail::_Node_iterator<std::pair<std::string const, int>, false, true>, std::__detail::_Node_iterator<std::pair<std::string const, int>, false, true> > const& ) [11] 0.0 0.00 0.00 32187 void std::string::_M_construct<char*>(char*, char\*, std::forward_iterator_tag) [8] So that looks like a std::vector<pair<string,int> > constructor taking two map iterators as input and an internal string member taking char pointer based iterators as input.