Lobbying won't help. This was done back in 15.0 when we added semantic partitioning. Ideally, we would have LIKED to include both the object_id and the partition_id......BUT.....the space in the table header would not support it. So we were faced with a choice of:
a) including both in the table header and force a page rewrite on upgrade and possibly a reindex if rows moved off the page due to insufficient space.
b) using the partition_id instead of object_id in the page header
We chose (b).
In the cases where the table is not partitioned (okay - a single round robin partition), the partition_id is same as object_id. For partitioned tables, you would need to look up the partition_id in syspartitions to find the corresponding object_id.....which is the best way to do it anyhow.
