I’m wondering if the following use of typedefs is any good practice, or if there are any downsides to it.

Basically I have alot of “data”-structs, which are intended to be used in (globally unique) containers, and they hold indices to other (globally unique) containers, the reason is to keep memory access localized. Rather than having the indice types be generic size_t I thought of naming them as follows for clarity:

typdef uint32_t MeshID;

typedef Mat4 Transform;
typedef std::vector<Transform>::size_type TransformIndex;

struct AABB
{
    AABB(const Vec3& center, const Vec3& extent);

    typedef std::vector<ModelMesh>::size_type AABBIndex;


    Vec3 mAABBCenter;
    Vec3 mAABBExtent;
};

struct ModelMesh
{
    ModelMesh(const MeshID meshID, const uint32_t aabbIndex, const uint32_t transformIndex);

    typedef std::vector<ModelMesh>::size_type ModelMeshIndex;


    const MeshID mMeshID;

    const AABB::AABBIndex mAABBIndex;
    const TransformIndex mTransformIndex;
};

struct ModelNode
{
    ModelNode(const uint32_t aabbIndex, const uint32_t transformIndex);

    typedef std::vector<ModelNode>::size_type ModelNodeIndex;


    const ModelNodeIndex mNodeStartIndex;
    const ModelNodeIndex mNodeEndIndex;

    const ModelMesh::ModelMeshIndex mMeshStartIndex;
    const ModelMesh::ModelMeshIndex mMeshEndIndex;

    const AABB::AABBIndex mAABBIndex;
    const TransformIndex mTransformIndex;
};

struct Model
{
    Model(const std::string& name, const Mat4& initialTransform, const Vec3& minBounds, const Vec3& maxBounds, const MeshID meshID, MaterialPtr material);
    Model(DX11Renderer& renderer, const JonsPackagePtr jonsPkg, const PackageModel& pkgModel, LoadMaterialFunc loadMaterialFunction);
    ~Model();

    bool operator==(const Model& m);
    bool operator==(const std::string& modelName);


    const std::string mName;
    const size_t mHashedID;

    const ModelNode::ModelNodeIndex mRootNodeIndex;
};

The motivation is so that the relation between the structs are clear. The downside is perhaps alot of definitions? Too chatty?

Overall, is this good practice?