Consider replacing `From<raw_slice> for Vec<T>` with `TryFrom<raw_slice> for Vec<T>`

If the size of the slice in bytes is not a multiple of `__size_of::` this very likely represents a bug in the program. Currently, we just take the maximum number of elements of `T` that fit into the slice, leaving the trailing bytes and not reporting any potential issue.

Having `TryFrom` here would clearly indicate the size mismatch.

Similar issue we have in `raw_slice::len::()` where the length is actually the maximum number of elements of `T` that fit into the slice. This can also be a source of bugs.

Start by locating the From for Vec implementation and raw_slice::len() mentioned in the issue. Review how these APIs handle slices whose byte length is not divisible by the element size, then verify that mismatches are reported and the length behavior is addressed consistently.

Written by the indexing model from the issue text.