Integer to pointer cast

[vihdzp]

I'm trying to use Miri on a small codebase of mine which depends on bitvec, and I'm getting warnings like this:

warning: integer-to-pointer cast
   --> C:\Users\vihdz\.cargo\registry\src\index.crates.io-6f17d22bba15001f\bitvec-1.0.1\src\ptr\span.rs:277:37
    |
277 |         self.ptr = NonNull::new_unchecked(addr_value as *mut ())
    |                                           ^^^^^^^^^^^^^^^^^^^^^ integer-to-pointer cast
    |
    = note: BACKTRACE on thread `mset::tests::nat`:
    = note: inside `bitvec::ptr::span::BitSpan::<bitvec::ptr::Mut>::set_address` at C:\Users\vihdz\.cargo\registry\src\index.crates.io-6f17d22bba15001f\bitvec-1.0.1\src\ptr\span.rs:277:37: 277:58
    = note: inside `bitvec::vec::BitVec::with_vec::<{closure@bitvec::vec::api::<impl bitvec::vec::BitVec>::push::{closure#0}}, ()>` at C:\Users\vihdz\.cargo\registry\src\index.crates.io-6f17d22bba15001f\bitvec-1.0.1\src\vec.rs:661:4: 661:61
    = note: inside `bitvec::vec::api::<impl bitvec::vec::BitVec>::push` at C:\Users\vihdz\.cargo\registry\src\index.crates.io-6f17d22bba15001f\bitvec-1.0.1\src\vec\api.rs:623:4: 623:42

It seems the issue is that this crate doesn't adhere to the still experimental strict provenance API. Is this a problem that can be dealt with, or is it just something to live with for the forseeable future?