Can boost::asio::thread_pool be used instead of combining boost::asio::io_context with a boost::thread::thread_group?

I'm trying to clear up some confusion I have. I stumbled over boost::asio::thread_pool and I thought that one could use to somehow automatically combine boost::asio::io_context and boost::thread::thread_group like is often suggested (here or here). It appears that this asio-specific pool can be used to post tasks to but, on the other hand, some networking types like resolver need to be passed an object io_context as a constructor parameter which thread_poolisn't and doesn't derive from.

#c++