Some good answers and points already, I'll just add a few more ideas to the pot.
ISO/IEC 27005 suggests that there are two groups of assets to be considered, primary and secondary. Primary assets are 'process' and 'information', secondary assets are everything else.
In your scope statement, it is normally a good idea to identify your major primary assets - since this is normally core to the reason you would be implementing ISO/IEC 27001. So it is typical to see 'customer information' identified in the scope statement, for example. This in-turn indicates to 'interested parties', customers in this case (and you also as the ISMS implementer), that any process, people, technology, etc. that touches on customer information (human, technical, physical, or whatever) will be appropriately considered -- regardless it is owned and managed by your company or it is outsourced.
Your VPN therefore, is a secondary asset and has value (is important) to your organization because customer information is travelling in-through-and out of the hole (assuming customer info from my example) and has a role in protecting the confidentiality, integrity, and availability of the information which travels through it - its a control; equally, it is a risk, since it can fail and render information unavailable. This is where scoping starts to get a little more complex, because we are probably now talking about boundaries and interfaces also - those parts of the process that cross over from being in-scope, to out-of-scope. I.e the information is starting inside of areas that you have control over (inside your business) and then going outside to areas that you have no control of (your ISP). Your ISP is an example which would be out-of-scope (its not your business and you have no control over their security environment) but represents a boundary and itself is an asset since you depend on them to send and receive information in your business.
So to make matters more complex, not all assets are things that are in-scope per say. Like personal mobile telephones, are they assets? Not owned by the company, but often used by employees to do their work -- and often containing highly sensitive and important business information.. so they are an asset. As is your home office, where you take your work home for the weekend, making it an asset, but likely out of scope.
So scope and assets are two different things. Scope is simply telling us where we can and will apply our ISMS Policies and procedures and what is covered in terms of core business and information. Boundaries, interfaces, and out-of-scope process are something we must be aware of so that we can assess the risks and put in place the appropriate controls and manage the risks, commonly done by way of contractual arrangements.
Scope statements will normally make reference to information (actual information - not the database that contains the information which is a secondary asset), processes, and locations. It doesn't have to be detailed and complicated, but as you have mentioned, is very important and should be accurate. It plots out the big picture for us from which we can dig in to the details.
The scope also gives us a starting point for our assets - so if customer information is mentioned, we can start to figure out where and how that information is used throughout the business processes - that leads us to want to draw up an asset register - so that we don't forget, and others can improve on our work in the future, etc. By following the process, we'll also start to identify those secondary assets, like the database that holds the information and needs to be available to users -- and then we find users become an asset, etc..
To answer then, your VPN and wireless access points would become assets as they are preserving the confidentiality, integrity, and availability of information of which is presumably in scope. If they are not a part of the process that you have identified from your scope, then they are not assets in the ISMS.
Last example.. draw a process diagram for a process that is in scope (inputs, activities, outputs, resources, controls/management) -- identify information that is created, used, destroyed.. etc within this process - the process and the information are your primary assets. Then look at how and what uses those assets within that process.. they are your secondary assets. It all goes into your asset inventory because this gives us the context of our risk assessment.
This is why scoping is so important, since its drives the implementation of the whole ISMS. Miss something important and the ISMS will add no value to your business. Include things that are irrelevant, and you will be burning valuable resources.
Which brings us to the next, even more important question when establishing the scope.. what is the purpose of the ISMS? A question that must be answered by top management. Answer that, and things will start to become more clear :)
And a last observation:- make sure you are using ISO/IEC 27001:2013 - since the 2005 version is now obsolete. From your post it kinda sounds like you might be looking at the 2005 version. In the new version, this issue is much clearer in my opinion. The starting point is Context of the Organization, leading you to conclude the scope of the ISMS. This concept was there in the 2005 version, but not spelled out as clearly.