Using find is also not needed as you know which item you need to check, even if you get it working (I believe that if you use Strings, aItem is a struct and they are the first element declared in the struct it will work as intended), you will be tossing away processing (as you need to find the element in the array).

Actually his implementation will always work regardless of where the string is stored in the same struct as he is providing an == operator which find will call for the data type you give it.

Also another tip: instead of doing index++, try to use ++index. In this case it doesn't matter but it is a good habit to have, so when you only want to increment and decrement a variable by 1 ever and nothing else write ++var or --var. The reason behind this is that the ++operator or --operator(both pre and post increment or decrement) can be overloaded and do a lot of work that is unnecessary in that particular case.

What do you mean by turning it into a class?

Also, please don't place extended logic inside switch statements. It's a nightmare to read. Check this out:

[source lang="cpp"]
void processItemSelect() {
int choice = -1;

while(choice == -1) {
cout << "Which item would you like to use?" << endl;
for(vector<aItem>::size_type index = 0; index < inventory.size(); ++index) {
cout << "Item " << index + 1 << ": " << inventory[index].itemName << endl;
}
cout << "MAKE YOUR CHOICE." << endl << "Choice: ";
cin >> choice;
--choice;
if((choice >= inventory.size()) || (choice < 0)) {
choice = -1;
cout << "Choice out of bounds. Stop being a dick." << endl << endl;
}
}
switch(inventory[choice].itemType) {
case ITEM_POTION:
cout << "You used a healing potion!" << endl;
break;
case ITEM_BALLS:
cout << "FIERY BALLS OF JOY!" << endl;
break;
default:
cout << "Invalid Item type" << endl;
break;
}
}

int main() {
int selection = 0;
cout << "This is a test game to use inventory items. Woo!" << endl <<
"You're an injured fighter in a fight- real original, I know." << endl <<
"1) Use an Item. 2) ...USE AN ITEM." << endl;
cin >> selection;

switch (selection) {
case 1:
processItemSelect();
break;
case 2:
cout << "Why do you have to be so difficult? Pick 1!" << endl;
break;
}

return 0;
}[/source]

Finally, do not prefix numeric literals with a zero. That's the notation for the octal numbering system:

10 is 10.
010 is 8.

Gaah, 2 posts while I was editing. Derp.

Ah, I see. You just mean implementing it. I'm glad to hear the you're enjoying your successes.

Edit - Occurred to mention it while I was outside - You would probably be better off placing the usage message in the item's effect processing. That way you just have to proc the item effect of the selected item instead of switching to print the usage message.

As long as you keep going you get 'there' in the end. ;)