Use library completely without std::allocator (operator new)

[Feierdeifel]

Hi,
Is it possible to use the library completely without a call to new operator.
I set the basic json to my containers and allocator.

namespace dynalloc {
using allocator = CountingAllocator<T>;  //Custom allocator
using string = std::basic_string<char, std::char_traits<char>, allocator<char>>;

template <typename Key, typename Tp, typename... Args>
using map = std::map<Key, Tp, Args...>;

template <typename Tp, typename _Alloc = allocator<Tp>>
using vector = std::vector<Tp, _Alloc>;
...

using JsonMb = nlohmann::basic_json<dynalloc::map,
                                    dynalloc::vector,
                                    dynalloc::string,
                                    bool,
                                    std::int64_t,
                                    std::uint64_t,
                                    double,
                                    dynalloc::allocator>;

This works but I still get calls to new() because the lib uses vector<> or make_shared<> in the code.
Basically I do nothing special with the lib. Just creating some json strings and dumping it to other functions

Because I am not able to check what happens in detail I wanted to ask the community if this is possible.
Regards

[ComputeUnit]

We would also like to know more information on this issue. We have an application that is running on an embedded device which uses a very strict memory allocation strategy. All memory allocations are wrapped with our own allocators, which are stl compatible, so that we can budget for all memory usage, down to the byte, by the various subsystems. When using this library and calling the 'dump' method, there is a global call to 'new' for the 'std::make_shared' inside the 'output_adapter' class constructor. Obviously this is on account of the 'output_adapter_t' using 'std::shared_ptr'.

Is there any way to avoid this?
Is our only option to go ahead and modify the calls to 'make_shared' to use 'allocated_shared' with a user-supplied allocator instead?

Kind regards