As described in my blog post here: http://phil-austin.blogspot.com/2010/08/data-dude-erroring-on-deployment-over.html only some database properties are available in VS database projects. In particular size and autogrowth settings are missing. This can cause deployment errors when the settings in the target database are different to the project being deployed. I often opt for non-default options and altering these settings requires some digging around for .sql files on the filesystem which is hardly ideal.
If the intention is to leave this up to the DBA I'd argue that a) the DBA should use the project as well and b) there are already settings in the project that might be regarded as DBA territory (such as collation settings). In any case the project will try to overwrite those settings - regardless of how they are set in the target database!
My suggestion would be to simply add auto-growth and size to the advanced property dialogue along with the other database settings.