ive run into the same issue, really is odd... doesnt this defeat the purpose entirely of touting it as a "cms like" capability?
I started by creating a custom post type called "Team"...and a regular page called "our team" wich acts as an index page... just a page template pulling in the custom "Team" pages.
in my case my custom post type is set to "page"... i set the 'supports' argument when registering the custom post type to include 'page-attributes' thinking this would let me bring in the default parent drop down... wich would open up the existing 'pages' to set one of them as the parent.
With the idea being that i could select the static "our team" page to be the parent. thereby integrating it all menu-wise.
but even though the page attributes box does appear in the custom write panel, the 'Parent' drop down menu only shows pages of this particular custom type (team pages) wich is unfortunate, and doesnt make sense to me as these pages are essentially siblings.
i had assumed this is what would have let us set ANY existing page as 'parent'... as it is, there doesnt seem to be a way to have a proper "top level" page for custom pages.
(on another note, the page template dropdown is missing entirely as well, wich was another surprise. it seems that the despite the term 'capability_type' A custom "page" type cannot use page template?
these custom post types dont quite actually do what posts/pages are capable of.
I was thinking of creating an "our team" top level page as a custom post type and setting it as the parent of the other team pages (since now it would appear as an option) and then running a conditional statement in the custom single post template... and adding in the appropriate code that way (single post code if its a child, get all posts code if its a parent)
But that would cause the same issue cippo mentioned above... double "parent" labels in the url. it could probably still work out with creative labeling, but it still means custom post types would always be 3 levels deep.
....good god i rambled