map->unordered_map in PropertySetMixin

no need to use an ordered map here, and an unordered map
is much faster.
Note that I leave the property name map alone, because
the ordering of that shows up in the output of some methods,
and some code is sensitive to non-ordered property names.

Change-Id: I34f9c516b6e5a981f789615fe986cd026c2ac8dd
Signed-off-by: Noel Grandin <noel.grandin@collabora.co.uk>
Reviewed-on: https://gerrit.collaboraoffice.com/c/online/+/9632
Tested-by: Jenkins CPCI <releng@collaboraoffice.com>
Reviewed-by: Mike Kaganski <mike.kaganski@collabora.com>
(cherry picked from commit 08443a9446cb1cfe1eae18955598f1a23a7a9aad)
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/210491
Tested-by: Xisco Fauli <xiscofauli@libreoffice.org>
Reviewed-by: Xisco Fauli <xiscofauli@libreoffice.org>

cppuhelper/source/propertysetmixin.cxx

@@ -22,6 +22,7 @@
 #include <algorithm>
 #include <cassert>
 #include <map>
+#include <unordered_map>
 #include <mutex>
 #include <set>
 #include <utility>
@@ -373,13 +374,13 @@ public:
     PropertySetMixinImpl::Implements implements;
     css::uno::Sequence< OUString > handleMap;
 
-    typedef std::map< OUString, BoundListenerBag > BoundListenerMap;
+    typedef std::unordered_map< OUString, BoundListenerBag > BoundListenerMap;
 
     typedef
     std::multiset< css::uno::Reference< css::beans::XVetoableChangeListener > >
     VetoListenerBag;
 
-    typedef std::map< OUString, VetoListenerBag > VetoListenerMap;
+    typedef std::unordered_map< OUString, VetoListenerBag > VetoListenerMap;
 
     mutable std::mutex mutex;
     BoundListenerMap boundListeners;