Arc::increment_strong_count design question

I think it's just implementation leaking into the API.

Instead of changing the counter directly, it reuses existing implementation via Arc::from_raw_in().clone(). This requires having a real instance of the Arc, which requires providing an allocator.