Need to audit for places where integer overflow may occur

Because this crate may be dealing with untrusted data, we should ensure that any functions involved in the process of parsing files are robust to large sizes, and return recoverable errors instead of panicking.

This has been partially addressed by the changed signature of `DType::num_bytes` to `Option<usize>` in (upcoming PR), but there's probably more issues still hiding beneath the surface.